-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix data-layout field in x86_64-unknown-linux-gnu.json test file #45108
Conversation
The value was generated according to [this comment by @japaric](rust-lang#31367 (comment)).
The change LGTM but the data-layout changed quite long time ago; why hasn't this break a test? It seems to me that this file is not being used at all. When Could you look into it @phil-opp? (TBH, I don't even know which test is supposed to be using this file.) |
It seems like the file wasn't actually used, since there is a built-in target with the same name. See rust-lang#45108 (comment) for more details.
Yeah, that wondered me too. I think that the file should be used by the I added a commit that renames the file to (I couldn't run the test locally, since I only have my laptop with a small SSD at the moment.) |
📌 Commit 06b9168 has been approved by |
Fix data-layout field in x86_64-unknown-linux-gnu.json test file The current data-layout causes the following error: > rustc: /checkout/src/llvm/lib/CodeGen/MachineFunction.cpp:151: void llvm::MachineFunction::init(): Assertion `Target.isCompatibleDataLayout(getDataLayout()) && "Can't create a MachineFunction using a Module with a " "Target-incompatible DataLayout attached\n"' failed. The new value was generated according to [this comment by @japaric](rust-lang#31367 (comment)).
The current data-layout causes the following error:
The new value was generated according to this comment by @japaric.